Skip to content

Conversation

heckj
Copy link
Member

@heckj heckj commented Mar 28, 2025

  • switched article titles to not use capitals all across
  • made use of swiftly more consistently lower-case, including titles
  • revised language in a few places to remove future or past tense phrasing or to make the wording more direct.
  • broke up the paragraphs into one-sentence-per-line structure for easier reviewing.
  • fixed an odd typo.
  • tried to broadly maintain the existing voice, but remove some extra phrasing here and there and generally tighten up the content.

- switched article titles to not use capitals all across
- made use of `swiftly` more consistently lower-case, including titles
- revised language in a few places to remove future or past tense phrasing or to make the wording more direct.
- broke up the paragraphs into one-sentence-per-line structure for easier reviewing.
- fixed an odd typo.
- tried to broadly maintain the existing voice, but remove some extra phrasing here and there and generally tighten up the content.
On macOS, download the pkg file and extract it like this from the command-line:

```
curl -L <location_of_swiftly_swift_org> > swiftly.pkg
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: Now that the download URL's are established, can you update this curl command here for macOS too?

Once the package is installed, run `swiftly init` to finish the installation:

```
~/usr/local/bin/swiftly init
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: since you're revamping the documentation now that things are settled, such the default location of the swiftly binary in the macOS .pkg file, can you update this path to be ~/.swiftly/bin/swiftly init?

```

# Proxy
# Installing toolchains through a proxy
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Maybe we should use the term "HTTP Proxy" here so that people don't confuse it with swiftly's toolchain binary proxy mechanism?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

excellent idea

Copy link
Member

@cmcgee1024 cmcgee1024 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

praise: This is a really good revamp to the documentation, thanks!

I've posted a few small questions and suggestions.

On macOS you can either run the pkg installer from the command-line like this or run the package by double-clicking on it (not recommended):

```
installer -pkg swift-x.y.z.pkg -target CurrentUserHomeDirectory
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: can the pkg file name be fixed here too? It's mistakenly written as swift-x.y.z.pkg when it should be swiftly-x.y.z.pkg.

@heckj
Copy link
Member Author

heckj commented Mar 31, 2025

@cmcgee1024 I added some revision of the Getting Started page in swiftly's docs to more closely mirror what's on the swift.org install pages. In particular, I dropped the swiftly-x.y.z.tar.gz structure, since it looks like this installer-to-install-swiftly wasn't released with versions embedded in its name.

That does highlight that there's a lot of repetition with the "getting started" docs and what's on in https://www.swift.org/install/linux/ & https://www.swift.org/install/macos/

The getting started doesn't mention explain this bit from the "install" page details though:

. ~/.swiftly/env.sh && \
hash -r

The env portion IS covered in shell-autocompletion, but we don't guide folks there, and we don't mention much of anything about the hash -r to get the shells "up to date" with the new commands installed. I added the "shell autocompletion" to see also at the bottom of the quick-start/Getting started page, but it might warrant adding the hash -r as a quick line before jumping into bits showing using the tooling. WDYT?

@cmcgee1024
Copy link
Member

we don't mention much of anything about the hash -r to get the shells "up to date" with the new commands installed

The swift website is focused more on getting users up and running very quickly, so it tries to accelerate them past all of the shell update commands too. I think for here we can rely more on swiftly itself informing the users of the followup commands. Let swiftly do the heavy lifting of guiding the users to help with documentation that may be more mismatched with the implementation.

@cmcgee1024
Copy link
Member

This looks great, thanks for the reworking the documentation @heckj.

@cmcgee1024 cmcgee1024 merged commit 10b08b2 into swiftlang:main Mar 31, 2025
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants